Skip to content

Conversation

@jmike
Copy link
Contributor

@jmike jmike commented Jan 22, 2025

Accept any nodejs version above v.14.

jmike added 2 commits January 22, 2025 10:07
Accept anything above node v.14, according to docs.
@jmike jmike requested a review from causaly-mark January 22, 2025 10:10
@changeset-bot
Copy link

changeset-bot bot commented Jan 22, 2025

🦋 Changeset detected

Latest commit: 167d365

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
aint Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@jmike jmike requested a review from codegaze January 22, 2025 10:10
@jmike
Copy link
Contributor Author

jmike commented Jan 22, 2025

@causaly-mark FYI you had previously set the node version to...

"engines": {
  "node": "^20.13.0",
  "npm": "^10.5.2"
}

...which causes npm install to fail with the following message when using the latest LTS...

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: aint@0.6.3
npm error notsup Not compatible with your version of node/npm: aint@0.6.3
npm error notsup Required: {"node":"^20.13.0","npm":"^10.5.2"}
npm error notsup Actual:   {"npm":"10.9.0","node":"v22.12.0"}

@jmike jmike merged commit 24fb822 into main Jan 22, 2025
3 checks passed
@jmike jmike deleted the fix-remove-strict-engine-check branch January 22, 2025 10:13
Copy link
Contributor

@causaly-mark causaly-mark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants